Project Management Models, Initiating, Planning, Executing, Controlling, and Closing: EDT732 Week 4 Wiki
Planning and analysis are the first two phases in developing large-scale technology projects. Keep in mind, there are never clear-cut steps for any project. Models, phases, and steps must be adapted for any specific project. This wiki is only providing suggestions for possible activities to consider when working through the planning and analysis phases of a project.
Planning The planning phase involves understanding why the project is needed (Dennis, Wixom, & Roth, 2015). Why are we building, or buying the technology? Planning also determines how the project will be structured (Dennis, Wixom, & Roth, 2015). FRRRAustralia (2014) identifies some of the elements found in project planning https://www.youtube.com/watch?v=UFeMVz6dam8.
The elements in the planning phase are scoping, feasibility, and project management. Project scope is identifying the needed technology. For example, a common need in organizations is an update to the phone systems. Feasibility involves technical, economic, and organization feasibility. Feasibility identifies who or what is needed to run the new project. For example if you are putting in a new learning management system, do you have personnel who know how the system operates? Will you need to hire new personnel? This video provides additional information on the planning phase https://www.youtube.com/watch?v=Do8iykQKMfU.
The most important aspect, and the aspect most often overlooked in the planning phase, is identifying best practices. If your organization is looking at a new integrated grading system, first review professional publications, and then identify organizations already using the system. Taking the time to get first hand assessment of the technology you are considering to buy will save frustration and money!
Analysis This very short video identifies the elements of the analysis phase http://www.youtube.com/watch?v=wlZkZganK-Y (Bokhowa, 2010). In the analysis phase you are looking for the gap between what is and what should be. According to Frendo (2013) you are gathering information (see his video http://www.youtube.com/watch?v=CuMpTq7V09s). The analysis phase answers the question what will the system do, who will use the system and why it is needed (Dennis et al., (2009).
The analysis phase is used for determining the results you want to achieve (Kaufman, Watkins, & Leigh, 2001). In systems thinking measurable performance requirements are identified before you start looking for the product. This means, you can’t say, “we will use Interactive White Boards to improve student grades”. Instead, the measurable performance might be, “students in grade K will determine the value of money, 10 cents or less using, pennies, nickels, and dimes”. The analysis must be precise and clear about what will be delivered (Kaufman et al, 2001). Once analysis has determined the objectives, products can be examined that will help reach the objectives.
According to Dennis et al, (2009) the purpose of any project is to create value for the organization. At each stage of a project all stakeholders should have a voice. By involving all stakeholders you support the successful implementation of the project (Kaufman et al, 2001). Remember the goal is not to acquire a new product; the goal is organizational improvement (Dennis et al, 2009). The planning and analysis phases help avoid the selection of a system before identifying measurable results and the needs of the stakeholders (Kaufman et al., 2001).
Optional Wiki Participation Activity – The optional wiki assignment, worth two participation posts, involves providing information on either the Planning or Analysis phases of a large scale technology project. Post your response on this wiki to help your classmates have a better understanding of what is involved in these phases. A reference is required! Remember, to post you must first be a member of this wiki. Once you have joined the wiki click, Edit (top right, to post and then Save (top right), to save your work. Make sure your name is included so you receive credit!
System Development life Cycle (Planning Phase) by Joe Omokheyeke
The systems development life cycle (SDLC) is the process of determining how an information system (IS) can support business needs, designing the system, building it, and delivering it to users (Dennis, Wixom, & Roth, 2015). The system development methodology is organized into four major activities known as phases (planning, analysis, design & implementation). These phases are further broken down into tasks and in some cases even subtasks. The tasks represent the work that must be done in the development of the software for the information system. According to Dennis et al., (2015), the number of phases can vary from organization to organization but the work that needs to be accomplished is usually the same.
The planning phase is the initial step of understanding why a new system should be developed and creating a plan on how the project team will make it happen (Dennis et al., 2015). The major activities in the planning phase include project identification, systems request, and conducting feasibility studies (Dennis et al., 2015). The objective of a feasibility study is to determine if the completion of the project is feasible within the parameters specified by the organization. Most feasibility studies are subjected to economic evaluation to determine if the project will provide a satisfactory return on investment. The use of economic feasibility study can assist management in understanding the value of the proposed project and to make the decision as to proceed or to stop the project. In addition to economic feasibility, the proposed project might be subjected to a technical feasibility to determine if the technology can be built and the organization feasibility determine how the technology will be used and supported by the information systems staff and the organization (Dennis et al., 2015).
Reference
Dennis, A., Wixom, B. H., & Roth, M. (2015). Systems analysis and design (6th Edition). Hoboken, NJ: John
Wiley & Sons, Inc.
Project/Research Planning Steps
The guide to planning an educational project planning is designed primarily for individuals looking to execute a project successfully. By following each step, they will be able to create a plan customized to their needs.
Identify a problem or area of interest from everyday life experiences, practical issues, past research, or theory. Pay attention to the feasibility of your topic and whether it can be executed systematically. Determine the resources needed to conduct the project, your interest level, its size, and complexity, as well as the value of your results or solution for both theory and practice.
To thoroughly describe the topic, create a statement that includes the educational topic or specific problem and the justification for the project.
Explore the research literature to gain an understanding of the current state of knowledge pertaining to your project. A review of prior research will inform you if your project has already been explored (and if a revision or replication is needed), how to design your project, what data collection methods to use, and how to make sense of the findings of your project once data analysis is complete. The use of triangulation useful, which refers to the use of multiple sources and methods for collecting data (Creswell, 1998; Leedy & Ormrod, 2001; Merriam, 1998). Reviewing prior research can also help with creating questions, what population to explore, and laying the theoretical groundwork for your project.
If you are conducting research, this step is sometimes used throughout the research process or after data is collected (e.g., grounded theory research).
Identifying a clear purpose and creating a purpose statement helps determine how the project is conducted, what design to use, and the question(s) or hypothesis (es) of your project. Rich, thick description involves writing out detailed descriptions of the participants and setting under study (Creswell, 1998; Merriam, 1998).Consider the implications. Implications are the practical ways your project will assist the field of education. These are the underlying goals, the rationales for, or the importance of your project. Implications are linked to your problem or topic, purpose, and question(s) or hypothesis (es).
Four general purposes for executing educational projects are to explore, describe, predict, or explain the relation between two or more educational variables.
Explore – an attempt to generate ideas about educational phenomenon
Describe – an attempt to describe the characteristics of educational phenomenon
Predict – an attempt to forecast an educational phenomenon
Explain – an attempt to show why and how an educational phenomenon operates
The purpose of your project will help you determine which project design you should follow.
Your project’s purpose will also help you develop the question(s) or hypothesis (es) of your project. A question is an extension of your purpose and specifically states the questions you will attempt to answer. Usually, project questions are used when your project purpose is more exploratory or descriptive.
A hypothesis states your expectations concerning the relation between two or more variables in the problem or your area of interest. Usually, a hypothesis represents an extension of a purpose or question by adding a prediction or explanation component.
Finally, conduct a proposal. The proposal is a detailed description of how the project will be conducted that includes the project title and project leaders’ names, statement of the problem and purpose, review of relevant literature, and the r question(s) or hypothesis(es). The proposal also includes a formal description of the procedure to be used in the project that includes the information or variables to be gathered, the participants of the project and potential benefits or risks, the design and procedure for gathering data, what data gathering method(s) will be used, and how the data will be analyzed. Remember to check who/what is involved sharing the interpretations of data obtained from various sources with the participants from which they were gathered and determining if they feel that the results are credible (Creswell, 1998; Leedy & Ormrod, 2001; Merriam, 1998).
References
Creswell, J.W. (1998). Qualitative inquiry and research design: Choosing among five traditions. Thousand Oaks: Sage Publications.
Leedy, P.D. & Ormrod, J.E. (2001). Practical research: Planning and design (7th ed.). Upper Saddle River, New Jersey: Merrill Prentice Hall.
Merriam, S.B. (1998). Qualitative research and case study applications in education. San Francisco: Jossey-Bass Publishers.
Contributed by Retta Salerno
Development Life CycleSystem Planning Phase
According to Dennis, Wixom, and Roth (2015), when considering a new information system, the planning phase explains why and how a project should be built. The planning phase can be broken down into two steps, project initiation and project management. Project initiation often begins with a system request, justifying the organization’s need and potential value of building a new system. Next, a team of IT staff members and the project sponsor conduct a feasibility analysis. The feasibility analysis includes the technical (is it possible), economic (does it increase value), and organizational (is it useful) feasibility? Technical feasibility evaluates whether it is possible, economic feasibility describes the potential value added to the business, and organizational feasibility investigates whether it is likely to be used (Dennis, Wixom, & Roth, 2015).
A steering committee considers the system request and feasibility analysis to determine whether the project should be implemented. If approved, the project enters project management, when the project manager develops a workplan, selects staff, and begins project plan development (Dennis, Wixom, & Roth, 2015). According to Cassidy (2016), these documents can be shared with the steering committee, executive management, and the IS organization to gather input. Buy-in can be improved, and input cab be gathered, while new suggestions can be considered, and more buy-in can be improved. contributed by Darlene Vann
Cassidy, A. (2016).A practical guide to information systems strategic planning. CRC press. Dennis, D., Wixom, B. H., Roth, R. M. (2015). Systems analysis and design (6th ed.). Hoboken, NJ: Wiley. Hoboken, NJ: John Wiley & Sons.
Dennis, A., Wixom, B. H., & Tegarden, D. (2009). System analysis design UML version 2.0: An object-oriented approach (3rd ed.). Hoboken, NJ: John Wiley & Sons.
Planning and analysis are the first two phases in developing large-scale technology projects. Keep in mind, there are never clear-cut steps for any project. Models, phases, and steps must be adapted for any specific project. This wiki is only providing suggestions for possible activities to consider when working through the planning and analysis phases of a project.
Planning
The planning phase involves understanding why the project is needed (Dennis, Wixom, & Roth, 2015). Why are we building, or buying the technology? Planning also determines how the project will be structured (Dennis, Wixom, & Roth, 2015). FRRRAustralia (2014) identifies some of the elements found in project planning https://www.youtube.com/watch?v=UFeMVz6dam8.
The elements in the planning phase are scoping, feasibility, and project management. Project scope is identifying the needed technology. For example, a common need in organizations is an update to the phone systems. Feasibility involves technical, economic, and organization feasibility. Feasibility identifies who or what is needed to run the new project. For example if you are putting in a new learning management system, do you have personnel who know how the system operates? Will you need to hire new personnel? This video provides additional information on the planning phase https://www.youtube.com/watch?v=Do8iykQKMfU.
The most important aspect, and the aspect most often overlooked in the planning phase, is identifying best practices. If your organization is looking at a new integrated grading system, first review professional publications, and then identify organizations already using the system. Taking the time to get first hand assessment of the technology you are considering to buy will save frustration and money!
Analysis
This very short video identifies the elements of the analysis phase http://www.youtube.com/watch?v=wlZkZganK-Y (Bokhowa, 2010). In the analysis phase you are looking for the gap between what is and what should be. According to Frendo (2013) you are gathering information (see his video http://www.youtube.com/watch?v=CuMpTq7V09s). The analysis phase answers the question what will the system do, who will use the system and why it is needed (Dennis et al., (2009).
The analysis phase is used for determining the results you want to achieve (Kaufman, Watkins, & Leigh, 2001). In systems thinking measurable performance requirements are identified before you start looking for the product. This means, you can’t say, “we will use Interactive White Boards to improve student grades”. Instead, the measurable performance might be, “students in grade K will determine the value of money, 10 cents or less using, pennies, nickels, and dimes”. The analysis must be precise and clear about what will be delivered (Kaufman et al, 2001). Once analysis has determined the objectives, products can be examined that will help reach the objectives.
According to Dennis et al, (2009) the purpose of any project is to create value for the organization. At each stage of a project all stakeholders should have a voice. By involving all stakeholders you support the successful implementation of the project (Kaufman et al, 2001). Remember the goal is not to acquire a new product; the goal is organizational improvement (Dennis et al, 2009). The planning and analysis phases help avoid the selection of a system before identifying measurable results and the needs of the stakeholders (Kaufman et al., 2001).
Optional Wiki Participation Activity – The optional wiki assignment, worth two participation posts, involves providing information on either the Planning or Analysis phases of a large scale technology project. Post your response on this wiki to help your classmates have a better understanding of what is involved in these phases. A reference is required! Remember, to post you must first be a member of this wiki. Once you have joined the wiki click, Edit (top right, to post and then Save (top right), to save your work. Make sure your name is included so you receive credit!
System Development life Cycle (Planning Phase) by Joe Omokheyeke
The systems development life cycle (SDLC) is the process of determining how an information system (IS) can support business needs, designing the system, building it, and delivering it to users (Dennis, Wixom, & Roth, 2015). The system development methodology is organized into four major activities known as phases (planning, analysis, design & implementation). These phases are further broken down into tasks and in some cases even subtasks. The tasks represent the work that must be done in the development of the software for the information system. According to Dennis et al., (2015), the number of phases can vary from organization to organization but the work that needs to be accomplished is usually the same.
The planning phase is the initial step of understanding why a new system should be developed and creating a plan on how the project team will make it happen (Dennis et al., 2015). The major activities in the planning phase include project identification, systems request, and conducting feasibility studies (Dennis et al., 2015). The objective of a feasibility study is to determine if the completion of the project is feasible within the parameters specified by the organization. Most feasibility studies are subjected to economic evaluation to determine if the project will provide a satisfactory return on investment. The use of economic feasibility study can assist management in understanding the value of the proposed project and to make the decision as to proceed or to stop the project. In addition to economic feasibility, the proposed project might be subjected to a technical feasibility to determine if the technology can be built and the organization feasibility determine how the technology will be used and supported by the information systems staff and the organization (Dennis et al., 2015).
Reference
Dennis, A., Wixom, B. H., & Roth, M. (2015). Systems analysis and design (6th Edition). Hoboken, NJ: John
Wiley & Sons, Inc.
Project/Research Planning Steps
The guide to planning an educational project planning is designed primarily for individuals looking to execute a project successfully. By following each step, they will be able to create a plan customized to their needs.
References
Creswell, J.W. (1998). Qualitative inquiry and research design: Choosing among five traditions. Thousand Oaks: Sage Publications.
Leedy, P.D. & Ormrod, J.E. (2001). Practical research: Planning and design (7th ed.). Upper Saddle River, New Jersey: Merrill Prentice Hall.
Merriam, S.B. (1998). Qualitative research and case study applications in education. San Francisco: Jossey-Bass Publishers.
Contributed by Retta Salerno
Development Life CycleSystem Planning Phase
According to Dennis, Wixom, and Roth (2015), when considering a new information system, the planning phase explains why and how a project should be built. The planning phase can be broken down into two steps, project initiation and project management. Project initiation often begins with a system request, justifying the organization’s need and potential value of building a new system. Next, a team of IT staff members and the project sponsor conduct a feasibility analysis. The feasibility analysis includes the technical (is it possible), economic (does it increase value), and organizational (is it useful) feasibility? Technical feasibility evaluates whether it is possible, economic feasibility describes the potential value added to the business, and organizational feasibility investigates whether it is likely to be used (Dennis, Wixom, & Roth, 2015).
A steering committee considers the system request and feasibility analysis to determine whether the project should be implemented. If approved, the project enters project management, when the project manager develops a workplan, selects staff, and begins project plan development (Dennis, Wixom, & Roth, 2015). According to Cassidy (2016), these documents can be shared with the steering committee, executive management, and the IS organization to gather input. Buy-in can be improved, and input cab be gathered, while new suggestions can be considered, and more buy-in can be improved.
contributed by Darlene Vann
References
Bokhowa, B. (2010) SDLC analysis phase. Retrieved from http://www.youtube.com/watch?v=wlZkZganK-Y
Cassidy, A. (2016).A practical guide to information systems strategic planning. CRC press.
Dennis, D., Wixom, B. H., Roth, R. M. (2015). Systems analysis and design (6th ed.). Hoboken, NJ: Wiley. Hoboken, NJ: John Wiley & Sons.
Dennis, A., Wixom, B. H., & Tegarden, D. (2009). System analysis design UML version 2.0: An object-oriented approach (3rd ed.). Hoboken, NJ: John Wiley & Sons.
Frendo. E. (2014). What is needs analysis? Retrieved from http://www.youtube.com/watch?v=CuMpTq7V09s
FRRRAustralia (2014). Developing a Project Plan. Retrieved from https://www.youtube.com/watch?v=UFeMVz6dam8
Kaufman, R., Watkins, R., & Leigh, D. (2001). Useful educational results: Defining, prioritizing & accomplishing. Lancaster, PA: Pro>Active Publications.
Project Management Videos, (2013). Project Planning Process: 5 Steps to Project Management Planning. Retrieved from
https://www.youtube.com/watch?v=Do8iykQKMfU
How to cite this wiki:
Entrekin, F. (2017). Project management models, initiating, planning, executing, controlling, and closing: EDT732 week 4 Wiki. Retrieved from https://edt732integratingtechnology.wikispaces.com/Week+4